Artifact: Requirements Management Plan
 Requirements Management Plan |
Describes the requirements documentation, requirement types and their respective requirements attributes, specifying the information and control mechanisms to be collected and used for measuring, reporting, and controlling changes to the product requirements. |
| Worker: | System Analyst |
| Enclosed in: | Software Development Plan |
| Template: | |
| Examples: | |
| More Information: | |
|
|
| Input to Activities: | Output from Activities: |
Purpose 
A Requirements Management Plan should be developed to specify the information and control mechanisms which will be collected and used for measuring, reporting, and controlling changes to the product requirements.
The purpose of the Requirements Management Plan is to describe how the project will set up requirements documents, requirement types and their respective requirement attributes and traceability.
Brief Outline
(hyperlinks into HTML template in a new window)
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Overview
2. Requirement Artifacts and Requirement Types
3. Requirement Attributes
3.1 Attributes for <type of requirement>
3.1.1 Status
3.1.2 Benefit
3.1.3 Effort
3.1.4 Risk
3.1.5 Stability
3.1.6 Target Release
3.1.7 Assigned To
3.1.8 Reason
4. Traceability Criteria
4.1 Criteria for <type of requirement>
Timing
Developed during inception. Updated at each major milestone.
Responsibility
The Worker: System Analyst is responsible for creating the Requirements Management Plan.
